Package delivery management systems and methods

ABSTRACT

A system and method for tracking and managing package delivery within a distribution network. Many events happen during the processing, moving, and delivery of a package. Systems and methods herein identify whether all expected events occur, whether scan locations are correct, whether delivery times are met, and other requirements. Problems or potential problems can be identified and corrected.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser.No. 62/958,900, filed Jan. 9, 2020, which is hereby incorporated byreference in their entirety and for all purposes.

BACKGROUND

The development relates to systems and methods to quantify packagedelivery performance, identify and correct operational issues, andensure satisfactory package delivery.

In one aspect described herein, a method for distributing itemscomprises receiving, in an interface, a request for delivery performanceinformation; requesting, by a server, item information for a pluralityof items in a distribution network; analyzing the item information forthe plurality of items according to one or more delivery criteria;determining, in the server, whether analysis indicates that any of theplurality of item fails to meet one or more delivery criteria;identifying a potential failure based on the determining any of theplurality of items fails to meet the one or more delivery criteria; andinitiating a corrective action to address the potential failure.

In some embodiments, the tem information comprises scan information andlocation information

In some embodiments, the one or more delivery criteria comprise aplurality of rules.

In some embodiments, the request for delivery performance informationcomprises a subset of the plurality of rules.

In some embodiments, the request for delivery performance informationcomprises a selection of geographic area.

In some embodiments, requesting item information comprises requestingthe item information for the plurality of items which are associatedwith the selected geographic area.

In some embodiments, identifying the potential failure comprisesidentifying a potentially failed piece of item processing equipmentwithin the selected geographic area.

In some embodiments, the request for delivery performance informationcomprises a selection of a period of time.

In some embodiments, requesting item information comprises requestingthe item information for the plurality of items which are associatedwith the selected period of time.

In some embodiments, the method further comprises generating, for eachof the plurality of items, a score based on determining whether any ofthe plurality of items fails to meet the one or more delivery criteriaand generating an overall score for the plurality of items based on thedetermined scores for each of the plurality of items.

Ain another aspect described herein, a system for distributing itemscomprises a processor configured to: receive, from an interface, arequest for delivery performance information; request item informationfor a plurality of items in a distribution network; analyze the iteminformation for the plurality of items according to one or more deliverycriteria; determine, in the server, whether analysis indicates that anyof the plurality of item fails to meet one or more delivery criteria;identify a potential failure based on the determining any of theplurality of items fails to meet the one or more delivery criteria; andinitiate a corrective action to address the potential failure.

In some embodiments, the tem information comprises scan information andlocation information

In some embodiments, the one or more delivery criteria comprise aplurality of rules.

In some embodiments, the request for delivery performance informationcomprises a subset of the plurality of rules.

In some embodiments, the request for delivery performance informationcomprises a selection of geographic area.

In some embodiments, the processor is further configured to request theitem information for the plurality of items which are associated withthe selected geographic area.

In some embodiments, the processor is further configured to identify apotentially failed piece of item processing equipment within theselected geographic area.

In some embodiments, the request for delivery performance informationcomprises a selection of a period of time.

In some embodiments, the processor is further configured to request theitem information for the plurality of items which are associated withthe selected period of time.

In some embodiments, the processor is further configured to generate foreach of the plurality of items, a score based on determining whether anyof the plurality of items fails to meet the one or more deliverycriteria and to generate an overall score for the plurality of itemsbased on the determined scores for each of the plurality of items.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other features of the disclosure will become morefully apparent from the following description and appended claims, takenin conjunction with the accompanying drawings. Understanding that thesedrawings depict only several embodiments in accordance with thedisclosure and are not to be considered limiting of its scope, thedisclosure will be described with the additional specificity and detailthrough use of the accompanying drawings.

FIG. 1 is a block diagram of an embodiment of a system for managingpackage delivery.

FIG. 2 is an exemplary view of a graphical user interface showingsummary information.

FIG. 3 is an exemplary view of a graphical user interface for packagedelivery.

FIG. 4 is an exemplary view of a graphical user interface for packagedelivery.

FIG. 5 is an exemplary view of a graphical user interface for packagedelivery.

FIG. 6 is a flow chart depicting an embodiment of a process forgenerating a package score.

DETAILED DESCRIPTION

A distribution network delivers packages to homes, businesses,customers, recipients, etc. The timely and correct delivery of packagesis desirable for recipients, and can be advantageous for thedistribution network. Ensuring timely and correct delivery of packagesinvolves gathering package delivery information in real-time, near realtime, on a daily basis, weekly basis, or on other time frame. Thepackage delivery information can be used to identify past trends,identify specific problem areas, predict trends, intervene when adelivery standard is in jeopardy, and to provide customers withvisibility and assurance that package delivery will meet customerrequirements.

A distribution network may comprise multiple levels. For example, adistribution network may comprise regional distribution facilities,hubs, and unit delivery facilities, or any other desired level. Anationwide distribution network, for example, may comprise one or moreregional distribution facilities having a defined coverage area (such asa geographic area), designated to receive items from intake facilitieswithin the defined coverage area, or from other regional distributionfacilities. The regional distribution facility can sort items fordelivery to another regional distribution facility, or to a hub levelfacility within the regional distributional facility's coverage area. Aregional distribution facility can have one or more hub level facilitieswithin its defined coverage area. A hub level facility can be affiliatedwith a few or many unit delivery facilities, and can sort and deliveritems to the unit delivery facilities with which it is associated. Inthe case of the United States Postal Service, the unit delivery facility(or delivery unit) may be associated with a ZIP Code. The unit deliveryfacility receives items from local senders, and from hub levelfacilities or regional distribution facilities. The unit deliveryfacility also sorts and stages the items intended for delivery todestinations within the unit delivery facility's coverage area.

The distribution network can use data from a variety of sources toassess and improve package delivery, including sorting equipment, mobilecomputing devices, customer service call centers, address managementsystems, and others. A central server, processor, or hub can coordinatea package tracking system, and can generate a variety of interfaces,reports, and actions for improving package delivery performance andcustomer experience. Although the term package is used here, one ofskill in the art would understand that the tracking and managementsystems described herein could be used for tracking many types of items,such as parcels, letters, flats, inventory items, containers, units inlogistics systems, and the like.

As used herein, the term item may refer to an individual article,object, agglomeration of articles, or container having more than onearticle within, in a distribution system. An item may be a letter,magazine, flat, luggage, package, box, or any other item of inventorywhich is transported or delivered in a distribution system or network.The term item may also refer to a unit or object which is configured tohold one or more individual items, such as a container which holdsmultiple letters, magazines, boxes, etc. The term item may also includeany object, container, storage area, rack, tray, truck, train car,airplane, or other similar device into which items or articles may beinserted and subsequently transported, as are commonly used indistribution systems and networks.

The features, aspects, and advantages of the present development willnow be described with reference to the drawings of several embodimentswhich are intended to be within the scope of the embodiments hereindisclosed. These and other embodiments will become readily apparent tothose skilled in the art from the following detailed description of theembodiments having reference to the attached figures, the developmentnot being limited to any particular embodiment(s) herein disclosed.

The system and method described herein relate to generating andcommunicating an expected delivery window. FIG. 1 depicts an embodimentof a system 100 for tracking and managing package delivery. The system100 comprises a server 110, a package database 120, a customer servicedatabase 130, a facility database 140, and a user interface 150.

The server 110 may comprise or be a component of a processing systemimplemented with one or more processors. The server 110 may be a networkof interconnected processors housed on one or more terminals. The one ormore processors may be implemented with any combination ofgeneral-purpose microprocessors, microcontrollers, digital signalprocessors (DSPs), field programmable gate arrays (FPGAs), programmablelogic devices (PLDs), controllers, state machines, gated logic, discretehardware components, dedicated hardware finite state machines, or anyother suitable entities that may perform calculations or othermanipulations of information. The server 110 may comprise a processor111 such as, for example, a microprocessor, such as a Power PC®processor, an Alpha® processor, a microcontroller, a multi-coreprocessor, an Intel CORE i5®, or i3® processor, an AMD Phenom®,A-Series®, or FX® processor, or the like. The processor 111 typicallyhas conventional address lines, conventional data lines, and one or moreconventional control lines. The processor 111 may be in communicationwith a processor memory 112, which may include, for example, RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM, or any other form of storage mediumknown in the art. The processor memory 112 may include, for example,software, at least one software module, instructions, steps of analgorithm, or any other information. In some embodiments, the processor111 performs processes in accordance with instructions stored in theprocessor memory 112. These processes may include, for example,controlling features and/or components of the package deliverymanagement system 100, and controlling access to and from, andtransmitting information and data to and from the server 110 and theconstituent components of the package delivery management system 100, aswill be described herein.

The server 110 comprises a system memory 113, configured to operatinginstructions and data for operation of the server 110. The system memory113 may comprise a database, a comma delimited file, a text file, or thelike. The server 110 is configured to coordinate and direct theactivities of the components of the system 100, and to coordinate use,directions, notifications, and other processes associated with thedistribution of items, to analyze data from connected sources, performanalytics, generate displays, alerts, notifications, and other processesand functions.

In some embodiments, the processor 111 is connected to a communicationfeature 114. The communication feature 114 is configured for wiredand/or wireless communication. In some embodiments, the communicationfeature 114 communicates via telephone, cable, fiber-optic, or any otherwired communication network. In some embodiments, the communicationfeature 114 may communicate via cellular networks, WLAN networks, or anyother wireless network. The communication feature 114 is configured toreceive instructions and to transmit and receive information amongcomponents of the system 100, and in some embodiments, with a centralserver (not shown) or other resource outside the system 100, as desired.

The server 110 is in communication with the package database 120. Insome embodiments, the package database 120 may comprise a processor,memory, databases, address and control lines, and other componentssimilar to those described herein for the server 110. In someembodiments, package database 120 may be configured to use theprocessor, memory, databases, address and control lines, and othercomponents of the server 110, or a combination of its own components andthe server 110's components. In some embodiments, the package database120 can be hosted on a server (not shown) external to system 100.

The package database 120 stores, processes, receives, and manipulatesdata regarding package delivery in the distribution network. The packagedatabase 120 can store, use, and process information gathered from othercomponents of the delivery network, such as sorting equipment, scanners,and the like. Any scan information generated when a package is scannedas it is inducted into and moves through the distribution network, andis ultimately delivered is stored in the package database 120. Thepackage database 120 can store scan information, such as informationabout scan events for packages, delivery points for the items to bedelivered, delivery schedules such as estimated delivery times anddates, and the like. The package database 120 is in communication with amobile computing device 122.

The mobile computing device 122 comprises one or more processors, aninterface, a scanning module, and a geolocation module. The scanningmodule can be used to scan computer readable codes on packages. Thecomputer readable code on the package can uniquely identify the packageto the distribution network. The computer readable code can include oneor more codes, such as barcodes, QR codes, RFID tags, etc. The computerreadable code can also be scanned on package processing equipment in adistribution facility in addition to the mobile computing devices 122.The geolocation module is in communication with GPS satellites and candiscover the specific location of the system 100 through itscommunications with the GPS satellites. In some embodiments, the GPSmodule 110 uses other position determining systems to determine thesystem 100's its exact location, such as GLONASS, COMPASS,multilateration, Wi-Fi detection, triangulation, or LORAN.

In some embodiments, the scanner is used to scan a package when it isloaded on a vehicle, when it is delivered, and at other times in thedistribution network. The geolocation module identifies the geographiclocation of the mobile computing device 122 on a regular interval, andwhen a scan is performed with the mobile computing device 122. Themobile computing device 122 provides location information correspondingto the scan information generated by the scanning module. The mobilecomputing device 122 generates and provides scan information and theassociated location information to the package database 120. Thelocation information can include the geographic location of a resource,delivery device, item processing equipment when a scan event or otherevent occurs. For example, the scan information can include the locationof the scanning device or mobile device at the time of a scan of apackage, a time of the scan, etc.

In some embodiments, the mobile computing device 122 can be similar tothe mobile delivery devices carried and/or used by resources within theUSPS.

The package database 120 is in communication with an address managementdatabase 124. The address management database stores, processes,receives, transmits, and/or manipulates data and information related todelivery points in the distribution network. The package database 120can store, for each package in the distribution network, the sender ofthe package, an intended recipient of the package, class of service, andthe like. The address management database 120 can store a geographiclocation, such as GPS coordinates, associated with each delivery point,each distribution network facility, and/or other locations, buildings,facilities, etc. The geographic location can be updated periodically orcontinuously by other systems and/or components of the distributionnetwork.

In some embodiments, when scan information and location information fora package scan are received for a delivery of a package, the packagedatabase 120 can request and/or receive the geographic location of thedelivery point to which the package was to be delivered. The packagedatabase 120 and/or the server 110 can compare the location informationwith the stored geographic location of the delivery point to determinewhether the delivery occurred at the correct delivery point.

The server 110 is in communication with the customer service database130. In some embodiments, the customer service database 130 may comprisea processor, memory, databases, address and control lines, and othercomponents similar to those described herein for the server 110. In someembodiments, the package database 130 may be configured to use theprocessor, memory, databases, address and control lines, and othercomponents of the server 110, or a combination of its own components andthe server 110's components. In some embodiments, the customer servicedatabase 130 can be hosted on a server (not shown) external to system100.

In some embodiments, the customer service database 130 can receive,store, use, manipulate, transmit, etc. information related to customerservice activities within the distribution network. For example, acustomer, recipient, or intended recipient of a package may call acustomer service center, submit a customer service query online, orcontact customer support via another avenue or interface. These customerservice requests can be input, modified, researched, resolved, etc., bymanual and/or automated systems. The information regarding theresolution, the instance of a customer service request, etc., are storedin the customer service database 130, and can be used to evaluate andassess package delivery performance. In some embodiments, the customerservice database 130 can store a transcript of a call received at acustomer service center. The customer service database 130 can employone or more tools to analyze the call transcript, either in audio ortextual form, to extract relevant data, such as type of complaint, dataor information provided to a customer, package numbers, resolutionstatus, and the like.

The customer service database 130 an also receive, store, use,manipulate, and/or utilize information from transactions at retailcounters or customer service counters, such as at a post office withinUSPS. When a customer provides a package for delivery at a post office,the information regarding the package to be sent can be stored in thecustomer service database 130, a label, barcode, etc., can be created,and the label, code, etc. and package information associated therewithcan be stored in the package database 120.

The server 110 is in communication with the facility database 140. Insome embodiments, the facility database 140 may comprise a processor,memory, databases, address and control lines, and other componentssimilar to those described herein for the server 110. In someembodiments, the facility database 140 may be configured to use theprocessor, memory, databases, address and control lines, and othercomponents of the server 110, or a combination of its own components andthe server 110's components. In some embodiments, the facility database140 can be hosted on a server (not shown) external to system 100.

The facility database 140 can store, receive, use, manipulate, transmit,etc., information related to facilities, the processing equipment at thefacilities, and the like. For example, the facility database 140 canstore and use information regarding package movement through thedistribution network, including prospective information about where apackage is expected to be at certain days/times as it moves through thedistribution network. Each package and its expected delivery date/time,any issues associated therewith, rerouting, delays, etc., can beidentified and stored in the facility database 140.

The server 110 is in communication with a user interface 150. The userinterface 150 can be a graphical user interface accessible tosupervisory or other personnel to display information regarding aparticular item and its completed or intended delivery. In someembodiments, the user interface 150 can display aggregate or cumulativepackage information for a variety of categories, such as by geographicregion, package type, day or week, and the like. The user interface 150can be modified and manipulated to display package information such aspackage scores, package metrics, graphical information, historicalinformation, and the like, as desired.

Various factors and information can be used by the server 110 togenerate performance information, such as item delivery performanceinformation. The delivery performance information can include packagescores, indications of passes and failures, etc. In some embodiments,the delivery performance information includes overall package scores262, and all the other information shown in FIG. 2 Table 1 depicts anexemplary list of factors or rules used in some embodiments of a packagescore, such as a “perfect package” score determination, including thecategory, a description, and a result.

TABLE 1 Rule Category Description Result  1 Overall Exempt Non PackageBarcodes Exempt  2 Overall Exempt Parcel Return Service Exempt  3Overall Exempt Letter (except Priority Mail and Priority Mail Express)Exempt  4 Service Date Military/International Outbound; Green CardExempt  5 Service Date N/A Scheduled Delivery Date (SDD) Not Yet ReachedExempt  5-1 Service Date N/A - Not Yet in USPS Possession Exempt  6Service Date Late Fail  7 Service Date Late, Missing Stop the Clock ScanFail  8 Service Date Late, FFA, Missing Delivery Fail  9 Service DateExpress Missing SDD Fail 10 Service Date Non Express Missing SDD Fail 11Scan Distance N/A In Office Exempt 12 Scan Distance N/A Not Enough DataExempt 13 Scan Distance Improperly Scanned by IMD Hand Held Fail 14 ScanDistance Delivery Scan Not At Location Fail 15 Scan Distance DeliveryScan Not At Location, Scanned In Office Fail* 16 Scan Distance PossibleIncorrect Park Point Location Failure Fail* 17 Scan Distance ScannedMultiple Pieces in Succession Location Failure Fail* 18 Visibility N/ASDD Not Yet Reached Exempt 18-1 Visibility Military - Missing Arrival atUnit Scan Exempt 19 Visibility Failed First Attempt Fail 20 VisibilityMissing Arrival at Unit Scan Fail 21 Visibility Missing Out for DeliveryScan (or “N/A In Office”) Fail (Exempt) 22 Visibility Missing AcceptanceScan Fail 23 Visibility Missing Origination Enroute Scan Fail 24Visibility Missing Destination Enroute Scan Fail 25 Visibility MissingAcceptable Delivery Event Scan Fail 26 Customer Inquiry Customer InquiryFail

The rules are evaluated by the server using the appropriate data fromthe system 100. The category column indicates the category ofperformance under which a rule is evaluated. An exempt category meansthat rule does not necessarily result in a failure or a lowered overallpackage score 262. For example, an item having a value which meets orfails an exempt rule may not necessarily receive a failing score orlower score. In some embodiments, an “Exempt” value means that there isinsufficient data to give a passing or failing score to an item, so theitem is excluded from the calculations and analysis.

A “Fail” value in the Result column indicates that an item which meets arule will receive a failing score for that rule. A “Fail*” value, suchas on Rule 15-17, indicates that there is possible failure, but thatadditional information is required prior to determining a failure. Anitem receiving a failing score for any of the rules will receive afailing score in the perfect package determination. In some embodiments,the server 110 can determine an item fails the perfect package scorewhen the item receives a “Fail” on two or more rules. In someembodiments, an item will not receive a failing score if the onlyfailing score is a “Fail*” score, such as for Rules 15-17.

Rule 1 analyzes the type of barcode or identifier on an item within thedistribution network. If an item having a computer readable codethereon, such as a barcode, is received in the distribution network, butthe barcode is for an item type other than a package, then the item isexempt for the package score. In some embodiments, the server 110 willnot calculate or determine an item score, will not assign a pass/failscore for the item or barcode, or the server 110 will provide a score,but the score will not be utilized in other systems or analytics. Thebarcode on an item can encode an item type. If the item type is otherthan a package based on the barcode or identifier as received in theserver 110, then under Rule 1, the server 110 determines that the itemis exempt from the package score processes described herein, and dataassociated with the exempt item is not used in the determinationsdescribed herein.

Rule 2 analyzes whether the package has a barcode or other identifierthereon, or other information associated with the item or with theidentifier that indicates that the package is a return parcel, such aswhen a customer returns merchandise to a merchant or sender. If thepackage is a return parcel, the server 110 determines the package isexempt from the package score process.

Rule 3 analyzes if the item is a piece of letter mail. As noted above,the barcode on an item can indicate the item type and the item class. Ifthe item type is a letter, and the item class is neither Priority Mailnor Priority Mail Express (or any other desired service class), then theserver 110 determines that the letter is exempt from the score processesherein. If the letter is Priority Mail or Priority Mail Express, orother desired service class, the server 110 determines that the letteris to be analyzed for package processes described herein.

Rules 4-10 relates to service date requirements. A service date can be arequired delivery date, a guaranteed delivery date, an induction date,and the like. The server 110 can analyze information from the packagedatabase 120 and the facility database 140 to determine whether servicedates are met. For example, if a scan, such as an induction scan, anitem processing equipment scan, or other scan occurs at a time after anexpected event, after a guarantee delivery date, etc., then the server110 can provide a failing score for the package.

Rule 4 analyzes items that are intended for shipment to US militarylocations or which is outbound for international shipment. Such itemswill be handled by other postal services or carriers which are not theUSPS. The server 110 determines that such items intended for overseasdestinations are exempt, as the USPS has little or no control over thedelivery of these items. These items are not used in the package scoreprocesses described herein.

Rule 5 analyzes whether a package has no scheduled delivery date, orwhether the package is not subject to schedule delivery daterequirements. This can occur with some service classes, and/or can be anoption selected by a sender. If the package does not have scheduleddelivery date (SDD) requirements, the server 110 determines that thepackage is exempt from the service date metrics described herein. Thepackage may still be analyzed under the other rules listed herein.

Rule 5-1 analyzes a package's SDD and determines whether the package isin the possession of the distribution network. The server 110 can querythe package database 120 to determine whether there has been aninduction scan for the package, or whether there have been any otherscans stored in the package database 120 for the package. The server 110can query the facility database 140 to determine whether there is anyvisibility information for the package. If there is no informationshowing the package has been received into the distribution network, theserver 110 determines that the package is exempt from service dateevaluation and the package processes described herein. In someembodiments, the server can determine that such a package is still usedin the package score processes herein, but no service date rules apply.That is, if the package fails a service date rule, the server 110 candetermine that the package does not receive a failing score in thepackage score.

Rule 6 analyzes whether a package was delivered by the SDD. The server100 receives information on SDD from the facility database 140 and/orthe package database 130 which was created when the package was created,requested, a label was generated, a service class was selected, acustomer requested a guaranteed delivery date, etc. The server 100queries the package database 120 for a delivery scan or an out fordelivery scan, which would have been generated from the mobile computingdevice 122. If the date and/or time of the delivery scan or the out fordelivery scan is after a scheduled delivery date for the package, theserver 110 determines that the package receives a failing score. In someembodiments, if the out-for-delivery or delivery event scan occurs laterin the day than an expected or guaranteed time, or is later than therequired or expected time, then the server 110 can determine the packageis late, and the package fails this rule and fails the service datemetric.

Rule 7 analyzes whether a stop-the-clock scan exists for the package. Astop-the-clock scan for a package can occur when a carrier scans, usingthe mobile computing device 122, the item for delivery at the deliverypoint. A stop-the-clock scan can also occur when the package is scannedvia the mobile computing device 122 for an attempted delivery, forexample, when a recipient is not available to sign for a package, orwhen physical conditions do not permit package delivery to a deliverypoint. In some embodiments, a package may have an out for delivery scanstored in the package database 120, but there is no correspondingstop-the-clock scan. This can occur if the carrier forgets to scan thepackage at the delivery point, if the barcode is not scannable, or for anumber of other reasons. If the package does not have a subsequentreturn to office scan, which would occur if the package had not beendelivered, it is assumed that the package was delivered, but not scannedat the delivery point. In these situations, where a stop-the-clock scanevent is expected but is missing for a package, the server 110determines that the package receives a failing score for the servicedate metric.

Rule 8 analyzes whether a failed first attempt has occurred for thepackage. The failed first attempt (FFA) can be indicated by a scan ofthe package at the delivery point where the carrier inputs the FFA. Insome embodiments, the server 110 infers an FFA when a package receivesan out for delivery scan, and then receives a return to unit scan. Thesescans are stored in the package database 120 or in another locationaccessible to the server 110. In these cases, the server 110 determinesthat a FFA has occurred, and the server 110 assigns a failing score inthe package score process.

Rule 9 analyzes whether an item of express mail missed the SDD. Theserver 110 analyzes the date and/or time of the delivery scan or out fordelivery scan from the package database 120. If the delivery scan or outfor delivery scan for the express mail item occurs after the SDD, theserver 100 determines that the express mail item fails the service datemetric.

Rule 10 analyzes whether an item of non-express mail which has an SDDmissed the SDD. The server 110 analyzes the date and/or time of thedelivery scan or out for delivery scan from the package database 120. Ifthe delivery scan or out for delivery scan for the mail item having anSDD occurs after the SDD, the server 100 determines that the mail itemfails the service date metric.

Rules 11-17 evaluate package delivery with regard to scan distance. Thescan distance is analyzed using data from the mobile computing device122, including scan location as described above, and comparing the scanlocation to the geographic information, such as geographic coordinatesor a geo-fence stored for intended delivery point of an item in theaddress management database 124. This analysis can occur in the packagedatabase 120 or in the server 110, as desired. Geofences or thresholddistances can be established for the scan distance analysis. In someembodiments, a geofence exists for each delivery point, and thatgeofence is stored in the address management database 124. If a scanoccurs in the geofence, the scan distance requirement can be satisfied,that is, a scan can be determined to have occurred at the correctdelivery point when the scan occurs within the stored geofence for thedelivery point.

In some embodiments, the scan distance threshold can be a fixeddistance, such as 5 meters from stored address coordinates. In someembodiments, the threshold can be a percentage of a geofence boundary.For example, a scan event occurring within one or two standarddeviations of an average geofence boundary distance can be determined tomeet a scan distance requirement. In some embodiments, the scan distancethreshold can change based on the type of delivery point. If thedelivery point is on a rural route, the threshold distance can be largerthan for a delivery point in an urban or suburban environment. Thesethreshold requirements can be stored and accessed by the server 110 inmaking the scan distance determinations.

Rule 11 analyzes whether a scan location is in an office, for example,in a Post Office or other facility of the USPS. For a scan event, theserver 110 analyzes the scan data, including the location data from thepackage database 120. The location data is compared to known locations,such as delivery points in the distribution network. The addressmanagement database 124 can also store geographic location information,such as a geofence, for distribution network facilities. If the scanlocation indicates that the package was scanned at a distributionnetwork facility, the scan is not analyzed for scan distance, and thisscan event is not included in the package score processes describedherein.

Rule 12 analyzes whether there is sufficient location information for ascan to make a determination. If a stored scan event for a package doesnot have geographic location data associated with it, or does not havesufficient location information, then the server 110 determines that thescan event is exempt, and it is not considered in the package scoreprocesses.

Rule 13 analyzes whether a package was improperly scanned at a retailfacility. The Intelligent Mail Device (IMD) can be a scanner used at aretail counter, such as at a post office. In some embodiments, a clerkat a retail counter can improperly scan a package, either on acceptanceor on handing a package to a customer. When a scan at a retail facilityis improper, the server 110 determines that the scan of that packagereceives a failing score. Some packages can be delivered to lockers,boxes, etc., within a distribution facility, such as a PO box or otherbox at a post office. The IMD scanner is used in the post office fordelivery scans. If the server 110 identifies that a package which is tobe delivered to a delivery point other than a location in a facility, orin a post office, is scanned with an in-office scanner or IMD (ratherthan with a carrier's mobile computing device 122), then the server 110determines that the package fails the scan distance metric. This couldoccur where a retail clerk or other office employee scans a package asdelivered at the post office with an IMD, rather than sending the itemout for delivery to the delivery point.

Rule 14 analyzes whether the delivery scan occurred at the deliverypoint. The server obtains and analyzes scan data, including deliveryscans and the associated location information from the package database120. The server 110 also receives the intended delivery point for thepackage from the package database 120, and the geographic locationinformation for the intended delivery point from the address managementdatabase 124, via the package database 120. The server 110 determineswhether the scan of the package occurred at the intended delivery point.This determination can be done by determining whether the location ofthe mobile computing device 122 at the time of the package scan waswithin a geofence established for the intended delivery point, or waswithin a threshold distance of the delivery point, as described herein.If the delivery scan occurred at a location other than the intendeddelivery point, but occurred, for example, at a different delivery point(which could indicate delivery to the incorrect address), the server 110determines that the package receives a failing score for the scandistance requirement in the package score process.

Rule 15 analyzes whether a delivery scan occurs at an office, such as apost office. In some embodiments, a carrier performs a delivery scan ata postal facility. The server 110 can analyze the location of thedelivery scan information received from the package database 120. If thescan occurs at a postal facility, the server 110 can evaluate additionalinformation, such as item type, service class, etc., for the packages.Some types of packages need only be scanned at the facility prior todelivery, so the server 110 will not determine that a package fails thescan distance metric based solely on the delivery scan occurring at anoffice or distribution network facility. If, however, a package has anitem type or service class which requires a delivery scan at thedelivery point, the server 110 will identify a delivery scan at anoffice for such a package as failing the scan distance metric.

Rule 16 analyzes scans at a park point. A park point can be a pointwhere a carrier parks a vehicle and takes packages in hand to deliverthe packages to a plurality of delivery points near the park point. Apackage can be scanned at a park point in order to streamline delivery,or to indicate that the package was removed from the vehicle. The server110 can analyze scan information for packages and determine whether theyoccurred a park points. The geographic locations of park points can bestored in the address management database 122 or in the facilitydatabase 140, or in any other desired location. If a scan occurred at apark point, then the server 110 may not take any action. If the scanoccurred at a possibly incorrect park point, the server 110 maydetermine that the package fails the scan metric. The server 110,however, may assess other metrics in addition to the park point scans,prior to generating a failing score on this rule. If the park point scanis the only failure, then the server 110 may not provide a failing scoreto the package.

Rule 17 analyzes whether a package has been scanned at the same place asmultiple other packages. The server 110 can identify that the deliveryscans for a plurality of packages have occurred at the same locationwithin a set period of time, e.g., a few minutes or less, or on the sameday. In some embodiments, this can be triggered if the server 110identifies that the location of the delivery scan for a package is notwithin a geofence for or at the intended delivery point. In this casethe server 110 can request information for other packages scanned at thesame location within a set time period. If a number of packages arescanned at the same location, this indicates that the carrier isimproperly scanning packages for delivery when the packages are not attheir respective intended delivery points. Such improper scanning canlead to mis-delivered packages. The server 110 will determine that oneor more of the packages whose delivery scans occur at the same locationreceive a failing scan distance metric.

In some embodiments, however, circumstances may dictate that thedelivery scans all occur at the same location. For example, wherepackages are delivered to parcel lockers, to PO boxes, to apartmentbuildings, cluster box units (CBUs), or other similar higher densitylocations, multiple scans at the same location do not indicate aproblem. In some embodiments, when the server identifies that multiplepackages have been scanned at the same location within a set period oftime, the server 110 can query the address management database 124either directly or indirectly, to identify the destination type. If thedestination type is a high density area, a parcel locker, a PO box,etc., then the server 110 does not determine that the package fails thescan distance metric.

Rules 18-26 relate to package visibility. Visibility for packagesdescribes package tracking information and knowledge of the location ofa package at each point as it moves through the distribution network.The visibility for packages can be determined using information from thepackage database 120 and the facility database 140.

Rule 18 analyzes whether the SDD for a package has been reached yet. Theserver 110 may perform all the analysis, and analyze all the rulesdescribed herein, at a given periodicity for all packages in thedistribution network, of for all packages in a geographic region, or forsome subset of packages in one or more geographic regions. For example,the server 110 may perform this action at the beginning of a day, theend of a day, once per shift, on demand, etc. When the server 110requests the information for all packages from the facilities database140, which can include all tracking information, and from the packagedatabase 120, the server can analyze each package for one or all therules herein, or some subset of the rules, depending on the time of day,the on-demand request, and the like.

When the server 110 analyzes all the packages in the distributionnetwork, if the visibility information from the facilities database 140indicates that a package is moving through the distribution network, andthe SDD is not yet reached, then the server 110 determines that thepackage is exempt from the package score processing described herein.

In some embodiments, the server 110 can forecast whether the package islikely to meet the SDD based on the existing information. If the server110 forecasts that the package is likely to miss its SDD, then an alertcan be generated, and the server 110 can send additional instructions tothe facilities database 140 to handle that package differently, such ason an expedited basis. The server 110 can take such action in responseto any of the rules described herein, and not just Rule 18. In someembodiments, the server 110 can cause the user interface 150 to displayan indication of the problem, or the pending problem.

Rule 18-1 analyzes whether an arrival at unit (AAU) scan is missing.When the AAU scan is missing for military packages, such as packagesintended for delivery to overseas military bases, or between militarybases, etc., the server 110 does not determine that the package receivesa failing visibility score.

Rule 19 analyzes whether a delivery scan was a failed first attemptscan. When a carrier delivers a package and the delivery is not able tobe completed for any reason and the package is brought back to thedelivery unit, a FFA is identified. The scan for the FFA can occur atthe delivery unit after the package is brought back or can occur at thedelivery point as the carrier performs a FFA delivery scan with themobile computing device 122. In some embodiments, the server 110 caninfer a FFA when an out for delivery scan occurs followed by a return tounit scan, without a delivery scan therebetween. If the server 110identifies a FFA, then the package fails the visibility metric.

Rule 20 analyzes whether there is a missing AAU scan. An AAU scan shouldoccur when an item arrives at a distribution network facility fromanother facility. As a package moves through the distribution network tovarious facilities, an AAU scan should occur at each facility toindicate that the package arrived at the intended facility. If theserver 110 identifies a missing AAU scan for a package (which is notrelated to the military as in Rule 18-1), the server 110 identifies thatthe package receives a failing score for the visibility metric. In someembodiments, the server 110 can identify a package scan on itemprocessing equipment from the facilities database 140. The server 110can determine whether there is an AAU scan associated with the packagewhich was scanned on item processing equipment. If there is noassociated AAU scan at the facility, the server 110 determines that thepackage was improperly received, and the package fails the visibilitymetric.

The server 110 can initiate an inquiry at other data sources todetermine where the package was inducted and what the issue was. Theserver 110 can query sources in the system 100 or other sources toidentify, based on visibility information, the likely induction point ofthe package. The server 110 can analyze the status of equipment at thelikely induction point to see if it has a noted failure or deficiency.The server 110 can initiate analysis of other packages or items thatwere inducted at that induction point to see if there is a pattern offailure at a particular indication point (such as a post office), in aspecific geographic area, etc. The server can provide notifications andinstructions via the user interface 150 when such problems areidentified.

Rule 21 analyzes whether the package has an out for delivery scan. Apackage to be delivered from a postal facility will be scanned at thefacility when loaded onto a vehicle or when a carrier takes the packageto the route for delivery. This informs the visibility systems that thepackage is on its way to be delivered that day. The server 110 canidentify packages that are to be delivered on a given day, based on thetracking information from the facility database 140. If the out fordelivery scan does not occur on the expected day, the server 110 canidentify that the package fails the visibility metric. In someembodiments, the server 110 can receive a delivery scan for a package,but there is no associated out for delivery scan. In these cases theserver can identify there is a missing out for delivery scan, and thepackage receives a failing score on the visibility metric.

Rule 22 analyzes whether an appropriate acceptance scan occurs for apackage. An acceptance scan should occur when the distribution networkpicks up a package from an entity for delivery. For example, if acommercial online retailer intended to ship an item via the USPS, thenUSPS would perform an acceptance scan when the USPS either picked up thepackage, or when the package was provided to USPS. The server 110 canidentify a missing acceptance scan when the server 110 identifies anyscan on distribution network equipment, but there is no associatedacceptance scan for the package. If there is no acceptance scan for thepackage, the server 110 determines that the package fails the visibilitymetric.

Rules 23 and 24 analyze whether the proper enroute scans occurred. Foreach leg of a packages movement through the distribution network,origination and destination enroute scans should be received. Thesescans provide visibility for packages as they move through the network.The server 110 analyzes the enroute data from the facilities database140 and determines whether origination and destination enroute scans arepresent. If either an origination or destination enroute scan ismissing, the server 110 determines that the package fails the visibilitymetric.

Rule 25 analyzes whether an acceptable delivery event scan has occurred.As described elsewhere herein, a delivery scan occurs, or should occur,when an item is delivered to a delivery point. The server 110 mayidentify such a situation where an out for delivery scan is seen andthere is no delivery scan and no return to unit scan for a package. Ifthe server 110 identifies that there is no acceptable delivery scan,then the server 110 determines that the package fails the visibilitymetric.

Rule 26 analyzes whether a customer inquiry occurred for a package. Theserver 110 queries the customer service database 130 to determinewhether, for a given package, there was a customer inquiry. The customerinquiry can be via an online inquiry, it can be identified via a call toa customer service center, or by some other channel, as describedelsewhere herein. If the server 110 identifies that there was a customerinquiry for a given package, that package fails the customer inquirymetric.

FIG. 2 depicts an embodiment of a graphical user interface displayingsummary information. An interface 250 displays information regardingpackage deliveries within the distribution network in a summary oroverview format. The interface 250 includes a score section 260, agraphical section 270, and a data selection section 280. The interface250 can display data according to a color key 252, which indicates theranges of scores displayed in color for easy recognition of problemareas.

The score section 260 includes an overall package score 262. The overallpackage score 262 displays a percentage of packages that have beendelivered which have obtained a “perfect package” score. The perfectpackage determination is made by the server 110 using many factorsobtained from the package database 120, the customer service database130, the facility database 140 and other factors, as desired.

The package scores for individual items are determined by the aboverules. The overall package score 262 shows that out of a plurality ofpackages whose data was analyzed, which can be in the range of millionsof packages, 81.4% passed, did not fail any of the Rules describedabove, or achieved a score of “perfect.” the package score rulesdescribed above. If a package failed any of the rules or metrics, thepackage was identified as a failure.

The score section 260 also includes a service date score 264, a locationscore 266, a visibility score 268, and a customer inquiry score 269.These scores can illustrate reasons for packages failing in the overallpackage score 262 The service date score 264 graphically depicts thenumber, percent, or quantity of packages which passed and which failedthe scan distance metrics and/or the rules related to service date. Insome embodiments, the service date score graphically shows thepercentage of packages that did and not fail Rules 4 through 10.

The location score 266 graphically depicts the number, percent, orquantity of packages which passed and which failed the scan distancemetrics and/or rules related to scan distance. In some embodiments, theservice date score graphically shows the percentage of packages that didand did not fail Rules 11-17 or, in some embodiments, Rules 13-17.

The visibility score 268 graphically depicts the number, percent, orquantity of packages which passed and which failed the visibilitymetrics and/or rules related to visibility. In some embodiments, theservice date score graphically shows the percentage of packages that didand did not fail Rules 18-25.

The customer inquiry score 269 graphically depicts the number, percent,or quantity of packages which passed and which failed the customerinquiry metrics and/or rules related to customer inquiry. In someembodiments, the service date score graphically shows the percentage ofpackages that did and that did not fail Rule 26.

The graphical scores described herein are not limited to only the rulesdescribed above. One of skill in the art, guided by this disclosure,would understand that package score data, delivery data, and the like,can be used, manipulated, evaluated, displayed, etc., in various ways,as needed to achieve a desired result in analyzing the data.

The graphical section 272 includes a failure factors pareto 272 and atrend graph 274. The failure factors pareto 272 displays information inbars as a number of packages which failed which Rules. As depicted,failure factors pareto 272 shows the number of packages that failed thelate service date standard, such as Rule 6 described herein. The failurefactors pareto 272 also shows a cumulative line depicting the percentageof all failures.

The trend graph 274 depicts the percent of packages over time receivinga perfect package score, that is, a package that did not fail any rules.The time period for the failure graph can be any desired time period,such as a week, a month, a quarter, a year, etc. The trend graph 274 canidentify times where more packages have errors in the process. The trendgraph 274 can also display trends over areas, or can be used to comparegeographic areas to each other. For example, the geographic areasserviced by the distribution network, at any level of granularity, canbe displayed on the trend graph to identify areas which have moreperfect packages and which have fewer perfect packages.

The server 110 can evaluate the trends either using the trend graph 274,using the data from which the trend graph 274 is produced, or via otherprocesses. The server 110 can identify times, locations, areas, whichare prone to errors. In some embodiments, the server 110 uses machinelearning tools to identify patterns in the data indicative of a problemor a prospective problem. The server 110 can identify which errors occurmost frequently in which geographic areas, and can automatically, or atthe request of a user, send instructions to a supervisor, to processingequipment, to scanning equipment, etc., to take action to correct aproblem. For example, if a particular geographic area has more failuresin AAU scans than other areas, the server 110 can indicate thatmaintenance is needed on item sorting equipment which performs AAU scansat a facility in that geographic area. The server 110 can identify whichfacilities have the highest volume of packages for a geographic area andcan identify the equipment at the high volume facilities as the likelysource of the problem.

In some embodiments, where an AAU scan, acceptance scan, or othersimilar problem occurs, the server 110 can identify that a package ispotentially missing, has been misrouted, a label has been damaged, orthe package is otherwise unaccounted for. The server 110 can initiate asearch for the package that should have been scanned but was notscanned. To find the package, a facility may have a mesh network ofdetectors to identify the location of a package within a facility, andthe server 110 can initiate the search action to identify the locationof the parcel missing a scan. In some embodiments, the server 110 cannotify a supervisor that an item did not receive the correct scan andcan prompt a search for the item.

In another example, the server 110 can identify that a certain deliveryunit, such as a post office, has a higher incidence of failures of outfor delivery scans and/or delivery event scans. The server 110 canidentify that there is a problem with one or more mobile computingdevices 122 used at that delivery unit, and can automatically, or at therequest of a user, notify regarding the problem, inactivate a mobilecomputing device 122, or take other action to correct a problem or apotential problem. In some embodiments, the server 110 can identify thata particular delivery resource is prone to errors or mistakes, andcorrective action can be taken.

The server 110 can proactively identify issues in the distributionnetwork as noted above. To illustrate, a customer may not have anyconcerns with a package delivery that fails the perfect package score,if the package is delivered on time. The failure of the perfect packagescore can indicate a problem that may, at a future time, affect deliverytimes and customer satisfaction. For example, a package can fail Rule 15or 17 because it the delivery scan occurred at a location other than thedelivery point, or occurred at the same location at about the same timeas several other delivery scans. The customer may receive the correctpackage on the expected date, but it may be only a matter of time untila mistake is made, and the incorrect package is delivered, or thepackage misses the delivery date because of a carrier error. The server110 identifies trends, problems, anomalies, outliers, etc., in the scoredata, and can take action to fix the situation. In the example above,the server 110 can cause the mobile communication device 122 to providea warning to the carrier when the delivery scan occurs outside thegeofence for the delivery point, or will not accept the delivery scanuntil the mobile communication device 122 is within the geofence for thedelivery point. In some embodiments, the server 110 will notify asupervisor at the facility where errors, problems, anomalies areindicated.

In some embodiments, the server 110 can employ machine learningalgorithms to identify potential problems based on past packageinformation. The machine learning network can be trained using packagedata and problems that arise, and the machine learning algorithm can betuned to identify a number of problems or issues before they arise.

The data selection section 280 includes sections for date 281, area 282,district 283, failure factors 284, scan pattern 285, and stop-the-clockscans 286. The date 281 provides graphical bars indicating a number ofpackages on an x-axis and a row of a particular dates. As shown, onFriday, July 2019, there were nearly 4 million packages tracked andanalyzed by the system 100. In some embodiments, the bars associatedwith the date can include color indicators of the perfect packagepercentage and the failure percentages. A user can click or select aparticular date to cause the user interface 250 to display all of thedescribed features for only the particular day selected.

The area 282 provides graphical bars indicating a number of packages onan x-axis and a row corresponding to geographic regions of thedistribution network. As shown, the Southern area has the highest numberof packages. In some embodiments, the bars associated with the area caninclude color indicators of the perfect package percentage and thefailure percentages. A user can click or select a particular area tocause the user interface 250 to display the described features for onlythe particular area selected.

When an area is selected from area 282, the district 283 menu willindicate the sub-areas or geographic areas within the selectedgeographic area. These sub-areas can be referred to as districts. Thedistrict 283 section performs similar to the area 282. Selecting one ofthe districts will update other features of the user interface 250 todisplay information, scores, trends, etc. for the selected district.

The failure factors 284 menu is similar to the area 282 and the district283. The failure factor 284 menu will show for the selected area 282 anddistrict 283 the highest or most frequent failure causes. The sanpattern 285 selects specific rules related to scans to allow the server110 or supervisor to focus on scan related issues to identify and remedyexisting problems and to identify and remedy issues that could becomeproblems.

The stop-the-clock scans 286 displays the types of stop-the-clock scansfor the selected date 281, area 282, and/or district 283. Thestop-the-clock scans can include the following categories: delivered, noaccess, arrival at pick-up point, held at office per customer request,forwarded, no secure location available, no authorized recipientavailable, insufficient address, business closed, etc. As noted above,all stop-the-clock scans which are not delivery scans, indicate a FFA,and fail Rule 19. Showing a number of packages and their associatedstop-the-clock scan categories can allow a supervisor to assess,explain, and/or remedy packages with FFAs. The server 110 can parse thestop-the-clock scan types and identify trends and take corrective actionas needed.

FIG. 3 depicts a user interface 350. The location user interface 350 canbe similar to user interfaces described elsewhere herein. The locationuser interface 350 can be displayed when a user selects a portion of theuser interface 250, for example, if a user selects the scan locationscore 266. The location user interface 350 can display package scoresdescribed elsewhere herein. The location user interface 350 can displayseveral graphs or visual data depictions related to packages which failscan location rules. The location user interface 350 can depict databroken down by zip code, mail class, route type, etc. For example, theserver 110 can identify a number of zip codes, such as 10 or 20, whichhave the worst package performance, and can display those in a zip codesection 351. The zip code list can vary by area or district as selectedon the location user interface 350.

In some embodiments, the location user interface 350 can show graphregarding scan distance to correct location. The server 110 candetermine the distances between the scan location and the correctdelivery location. The server 110 can cause the distances to bedisplayed on the location user interface in a scan distance section 352.The server 110 can display either only those packages who failed thescan distance metric, or all packages categorized by distance to correctdelivery points. The scan distance section can display bars indicating anumber or percent of packages which fall within a distance category. Forexample, the distance categories displayed are >250 feet, >500feet, >1000 feet, although any distance could be used without departingfrom the scope of the current disclosure.

The location interface 350 can also show bar graphs indicating thenumber of failures or passes broken down by area, district, ZIP code,etc. The location interface 350 can also show the number or rate offailures by address type, route type, mail class, etc. The locationinterface 350 can further show charts or graphs of the type of locationfailure such as location failure type, scan distance, etc. These can begenerated by the server 110 by identifying which rules packages failedmost frequently, or which category of rules packages failed mostfrequently.

FIG. 4 depicts a customer inquiry user interface 450. The customerinquiry user interface 450 can be similar to user interfaces describedelsewhere herein. The customer inquiry user interface 450 can bedisplayed when a user selects a portion of the user interface 250, forexample, if a user selects the customer inquiry score 269. The customerinquiry user interface 450 includes metrics obtained from the customerservice database 130, such as the type of product, route type, the casepattern, resolution, and the like. The customer inquiry user interface450 can include categories of issues from the customer service database130, such as late, FFA, etc. The customer inquiry user interface 450 canshow metrics or graphs of data generated by the server 110, and can showfailures by area, district, which factors caused failure, the mostcommon last scan event before failure, time between a scan event and aninquiry, etc.

FIG. 5 depicts a FFA user interface 550. The FFA user interface 550 canbe similar to user interfaces described elsewhere herein. The FFA userinterface 550 can be displayed when a user selects a portion of the userinterface 250, for example, if a user selects the a failure factor 284,or other portion of the user interface 250, as desired. The FFA userinterface 550 can display detailed information regarding FFA reasons asreceived from the mobile communication devices 122, dates of FFAs,trends of FFAs by region, area, district, etc.

FIG. 6 is a flow chart depicting an embodiment of a process forgenerating a package score. A process 600 begins in block 602. Theprocess 600 moves to block 604, wherein the server 110 identifiespackages for analysis.

The server 110 can identify packages for analysis a variety of differentways, each of which is explicitly contemplated by the presentdisclosure. In some embodiments, the server 110 can query the packagedatabase 120 for all packages for which package records exist for aspecified time period. Each package receives a unique identifier, andthe unique identifier is associated with the package and packageinformation in the package database 120. The server 110 analyze allpackages from the specified time period according to the process 600. Insome embodiments, the server 110 analyzes packages from only a givengeographic area. In some embodiments the serve 110 analyzes packagesfrom all geographic areas individually and then combines the informationfrom all geographic areas into an overall analysis.

In some embodiments, the server can identify for analysis those packagesanalysis for which an active package record exists. The package recordscan be entries in the package database 140 which are active, that is,which have not yet been delivered, or which have not expired fromnon-use. The server 110 can proceed with the method 600 for each packagehaving an active record.

In some embodiments, the server 110 can identify packages which havebeen inducted and for which an acceptance scan exists. This indicatesthat the distribution network is in physical possession of these items.In some embodiments, the server 110 can run an analysis under Rule 5-1on all packages and can exempt from further analysis any package deemedexempt.

In some embodiments, the server 110 can identify any group, subset,classification, or other categorization of packages for analysis. Insome embodiments, the server 110 runs the analysis every day, everyweek, every shift, or at any other desired periodicity. In someembodiments, the server 110 can identify packages which have beendelivered over a given time period, within a given geographic area, orwithin a geographic area within a given time. In some embodiments, amailer or shipper of items can request the server 110 provide analysisof packages which the sender or shipper sent.

The process 600 moves to block 606, wherein the server 110 obtainsinformation for each identified package. The server 110 queries thepackage database 120, the customer service database 130, the facilitiesdatabase 140, and any other data sources for package information. Thepackage information can be similar to that described elsewhere herein,for example, with regard to Rules 1-26.

The process 600 moves to block 608, wherein the server 110 analyzes theobtained package information. The server 110 can analyze the obtainedpackage information according to Rules 1-26 described herein. In someembodiments, the server 110 can analyze only a subset of the rulesdescribed herein, and/or can analyze for any additional characteristic,status, etc., as desired. In some embodiments, the server 110 analyzesthe obtained package information to generate scores for service date,scan distance, visibility, and customer inquiry separately orconcurrently.

In some embodiments, the server 110 uses the information and algorithmsdescribed herein to determine whether the packages identified foranalysis fail a rule, criterion, or requirement for a package score.

The process 600 moves to decision state 610, wherein the server 110determines whether the packages fail any rule. For example, the server110 analyzes the package information for the identified packages todetermine whether the package information indicates that the packagefailed to meet any rule. In some embodiments, the server 110 analyzeswhether other criteria is met or not met. As noted elsewhere herein,some rules or criteria may not lead to a failing package score bythemselves. Some rules may only be failed under certain conditions. Insome embodiments, the server 110 can determine how many rules arefailed, and if the percent of rules failed is small enough, the packagecan get a non-failing score. In some embodiments, the package score isnot a fail/no fail binary score, but is a percentage. In someembodiments, the rules can be weighted as desired to generate apercentage score.

If the package is determined not to fail the package score analysisaccording to the criteria established, the process 600 moves to block612, wherein the package is assigned a perfect package score. If thepackage is determined to fail the package score analysis, the process600 moves to block 614, wherein a failing score is assigned. The server110 initiates corrective action, sends notifications, etc., as describedherein.

In some embodiments, corrective actions can be initiated automaticallybased on a threshold number of items failing a certain rule, a certainnumber of items failing within a geographic area, a number of itemsfailing which have passed through a certain distribution facility, whichare assigned to a particular deliver resource, etc. For example, if theserver 110 identifies that a particular facility, a particular piece ofitem processing equipment, a mobile delivery device, or carrier has athreshold number of failures, has a higher number of failures than theaverage, or any other determination, the server can initiate correctiveactions by requesting maintenance on an item, by requesting furtherinformation from a piece of item processing equipment or carrier formore in-depth analysis. The corrective action can be providing an alert,by running a maintenance program, performing maintenance, running adiagnostic check, etc.

If, for example, if one machine or mobile delivery device have a highernumber of items processed therewith that fail, the server 110 can causefurther items not to be processed by the machine or mobile deliverydevice which has the higher than average or too-high number of failures.If a certain mobile delivery device, for example, is associated with ahigher than average or too-high number of failures, such as failures ofout for delivery scans, the server 110 can determine that the mobiledelivery device should be taken out of service, inactivated, and/or thatmaintenance needs to be performed on that mobile delivery device. Insome embodiments, if a certain mobile delivery device has a high numberof wrong location scans, the server 110 can inactivate the mobiledelivery device, prevent logging in to that device, etc. If a particularroute has a high number of failures due to wrong location scans, theserver 110 can initiate actions to determine whether the failures are aresult of inaccurate GPS coordinates for delivery points, or due toanother factor. If a route is classified as an urban route where theremay be more interference with accurate GPS signals due to tall buildingsor other factors, the server 110 can change or expand geofences, requestadditional or more frequent scans of items, and the like in order todetermine the cause of the increased number of failures.

If a certain piece of item processing equipment is associated with ahigh number of failures due to late delivery, such as not meeting anSSD, the server 110 can reroute items processed in the facility wherethe item processing equipment is located to another piece of itemprocessing equipment.

These corrective actions described herein are exemplary only. A personof skill in the art, guided by this disclosure, can identify othercorrective actions without departing from the scope of this disclosure.

The process moves to block 616, wherein the server generates anddisplays package score information on the user interface 150. Theprocess 600 then ends.

Various illustrative logics, logical blocks, modules, circuits andalgorithm steps described in connection with the implementationsdisclosed herein may be implemented as electronic hardware, computersoftware, or combinations of both. The interchangeability of hardwareand software has been described generally, in terms of functionality,and illustrated in the various illustrative components, blocks, modules,circuits, and steps described above. Whether such functionality isimplemented in hardware or software depends upon the particularapplication and design constraints imposed on the overall system.

In one or more aspects, the functions described herein may beimplemented in hardware, digital electronic circuitry, computersoftware, firmware, including the structures disclosed in thisspecification and their structural equivalents thereof, or in anycombination thereof. Implementations of the subject matter described inthis specification also can be implemented as one or more computerprograms, e.g., one or more modules of computer program instructions,encoded on a computer storage media for execution by, or to control theoperation of, data processing apparatus.

If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable storage medium. The steps of a method or algorithmdisclosed herein may be implemented in a processor-executable softwaremodule which may reside on a computer-readable storage medium.Computer-readable storage media includes both computer storage media andcommunication media including any medium that can be enabled to transfera computer program from one place to another. A storage media may be anyavailable media that may be accessed by a computer. By way of example,and not limitation, such computer-readable media may include RAM, ROM,EEPROM, CD-ROM or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium that may be used tostore desired program code in the form of instructions or datastructures and that may be accessed by a computer. Also, any connectioncan be properly termed a computer-readable medium. Disk and disc, asused herein, includes compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and Blu-ray disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above can also be includedwithin the scope of computer-readable storage media. Additionally, theoperations of a method or algorithm may reside as one or any combinationor set of codes and instructions on a machine readable storage mediumand computer-readable storage medium, which may be incorporated into acomputer program product.

Certain features that are described in this specification in the contextof separate implementations also can be implemented in combination in asingle implementation. Conversely, various features that are describedin the context of a single implementation also can be implemented inmultiple implementations separately or in any suitable subcombination.Moreover, although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemscan generally be integrated together in a single software product orpackaged into multiple software products.

Instructions refer to computer-implemented steps for processinginformation in the system. Instructions can be implemented in software,firmware or hardware and include any type of programmed step undertakenby components of the system.

As can be appreciated by one of ordinary skill in the art, each of themodules of the invention may comprise various sub-routines, procedures,definitional statements, and macros. Each of the modules are typicallyseparately compiled and linked into a single executable program.Therefore, the description of each of the modules is used forconvenience to describe the functionality of the system. Thus, theprocesses that are undergone by each of the modules may be arbitrarilyredistributed to one of the other modules, combined together in a singlemodule, or made available in a shareable dynamic link library. Furthereach of the modules could be implemented in hardware. A person of skillin the art will understand that the functions and operations of theelectrical, electronic, and computer components described herein can becarried out automatically according to interactions between componentswithout the need for user interaction.

The foregoing description details certain embodiments. It will beappreciated, however, that no matter how detailed the foregoing appearsin text, the development may be practiced in many ways. It should benoted that the use of particular terminology when describing certainfeatures or aspects of the development should not be taken to imply thatthe terminology is being re-defined herein to be restricted to includingany specific characteristics of the features or aspects of thedevelopment with which that terminology is associated.

While the above detailed description has shown, described, and pointedout novel features of the development as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the technology without departing from the intent ofthe development. The scope of the development is indicated by theappended claims rather than by the foregoing description. All changeswhich come within the meaning and range of equivalency of the claims areto be embraced within their scope.

What is claimed is:
 1. A method for distributing items, the methodcomprising: receiving, in an interface, a request for deliveryperformance information; requesting, by a server, item information for aplurality of items in a distribution network; analyzing the iteminformation for the plurality of items according to one or more deliverycriteria; determining, in the server, whether analysis indicates thatany of the plurality of item fails to meet one or more deliverycriteria; identifying a potential failure based on the determining anyof the plurality of items fails to meet the one or more deliverycriteria; and initiating a corrective action to address the potentialfailure.
 2. The method of claim 1, wherein the tem information comprisesscan information and location information
 3. The method of claim 1,wherein the one or more delivery criteria comprise a plurality of rules.4. The method of claim 3, wherein the request for delivery performanceinformation comprises a subset of the plurality of rules.
 5. The methodof claim 1, wherein the request for delivery performance informationcomprises a selection of geographic area.
 6. The method of claim 5,wherein requesting item information comprises requesting the iteminformation for the plurality of items which are associated with theselected geographic area.
 7. The method of claim 6, wherein identifyingthe potential failure comprises identifying a potentially failed pieceof item processing equipment within the selected geographic area.
 8. Themethod of claim 1, wherein the request for delivery performanceinformation comprises a selection of a period of time.
 9. The method ofclaim 8, wherein requesting item information comprises requesting theitem information for the plurality of items which are associated withthe selected period of time.
 10. The method of claim 1, furthercomprising generating, for each of the plurality of items, a score basedon determining whether any of the plurality of items fails to meet theone or more delivery criteria and generating an overall score for theplurality of items based on the determined scores for each of theplurality of items.
 11. A system for distributing items, the systemcomprising: a processor configured to: receive, from an interface, arequest for delivery performance information; request item informationfor a plurality of items in a distribution network; analyze the iteminformation for the plurality of items according to one or more deliverycriteria; determine, in the server, whether analysis indicates that anyof the plurality of item fails to meet one or more delivery criteria;identify a potential failure based on the determining any of theplurality of items fails to meet the one or more delivery criteria; andinitiate a corrective action to address the potential failure.
 12. Thesystem of claim 11, wherein the tem information comprises scaninformation and location information
 13. The system of claim 11, whereinthe one or more delivery criteria comprise a plurality of rules.
 14. Thesystem of claim 13, wherein the request for delivery performanceinformation comprises a subset of the plurality of rules.
 15. The systemof claim 11, wherein the request for delivery performance informationcomprises a selection of geographic area.
 16. The system of claim 15,wherein the processor is further configured to request the iteminformation for the plurality of items which are associated with theselected geographic area.
 17. The system of claim 16, wherein theprocessor is further configured to identify a potentially failed pieceof item processing equipment within the selected geographic area. 18.The system of claim 11, wherein the request for delivery performanceinformation comprises a selection of a period of time.
 19. The system ofclaim 17, wherein the processor is further configured to request theitem information for the plurality of items which are associated withthe selected period of time.
 20. The system of claim 11, wherein theprocessor is further configured to generate for each of the plurality ofitems, a score based on determining whether any of the plurality ofitems fails to meet the one or more delivery criteria and to generate anoverall score for the plurality of items based on the determined scoresfor each of the plurality of items.